Skip to content

fix(test): skip VM tests before booting extra VMs, unmount every node for fsck - #82

Merged
mattmattox merged 1 commit into
mainfrom
fix/vm-skip-before-cluster-setup
Nov 13, 2026
Merged

mattmattox merged 1 commit into
mainfrom
fix/vm-skip-before-cluster-setup

Conversation

@mattmattox

Copy link
Copy Markdown
Contributor

Since #72, "fsck Repair After Power Failure" fails on every 2-node VM run. Three 3-VM tests booted and mounted VM 3 before their NODE_COUNT skip, and fsck then refused to run because of VM 3's heartbeat (found by the per-node-journal session: 6 of 6 failures with VM 3 mounted, 2 of 2 passes without).

The tests now skip before booting anything, so no skipped test leaves a VM behind. The fsck test also unmounted only VMs 1 and 2, which broke 3-node runs, so it now unmounts and remounts every node.

Full 2-node VM suite on .68 (before rebasing onto #79): 57 passed, 0 failed. VM 3 never booted. The 3-node run is untested.

🤖 Generated with Claude Code

… for fsck

The three 3-VM tests and the concurrent directory test booted and mounted
the VMs they need before checking NODE_COUNT. On a 2-node run VM 3 stayed
mounted after they skipped, so fsck in the power-failure repair test saw
its heartbeat and refused to run. That test also unmounted only VMs 1 and
2, so it failed on 3-node runs too.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mattmattox
mattmattox merged commit 13fc94f into main Nov 13, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant